Systems Enabling Doctors to Access Medical Device Data

ABSTRACT

An example method is performed by a defibrillator and includes obtaining event data regarding treatment provided to a patient. The method also includes obtaining a key that facilitates validating a request from a computing device to access the event data, associating the key with the event data, and transmitting the key and the event data to a server. Another example method is performed by a mobile device and includes obtaining an encoded version of an identifier of a medical device that is provided on the medical device. The medical device is configured to obtain event data regarding treatment provided to a patient. The method also includes obtaining a selection of a recipient for the event data, and causing a summary of the event data to be transmitted to the recipient.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims priority to U.S. provisional applicationNo. 63/088,772, filed on Oct. 7, 2020, the entire contents of which areherein incorporated by reference.

BACKGROUND

During a cardiac arrest, a defibrillator, such as an automated externaldefibrillator (AED), can provide potentially lifesaving defibrillationtreatment. For instance, a defibrillator is configured to supply acharge through the patient's heart via a set of defibrillation pads of atherapy cable. The defibrillation pads are located at a first end of thetherapy cable and applied to chest of a patient. At a second end of thetherapy cable, a connector couples the therapy cable to an electricalsource of the defibrillator that is configured to generate a shock.

SUMMARY

Within examples described herein, systems and methods are described thatallow medical professionals involved in treatment of a patient to accessevent data regarding previous treatment provided to the patient while adefibrillator was attached to the patient.

Within additional examples described herein, defibrillation pads aredescribed that include mechanisms for imprinting a key on a patient'sskin.

Within additional examples described herein, systems and methods aredescribed that include causing a summary of event data regardingtreatment provided to a patient to be transmitted to a selectedrecipient for the event data.

The features, functions, and advantages that have been discussed can beachieved independently in various examples or may be combined in yetother examples. Further details of the examples can be seen withreference to the following description and drawings.

BRIEF DESCRIPTION OF THE FIGURES

The novel features believed characteristic of the illustrative examplesare set forth in the appended claims. The illustrative examples,however, as well as a preferred mode of use, further objectives anddescriptions thereof, will best be understood by reference to thefollowing detailed description of an illustrative example of the presentdisclosure when read in conjunction with the accompanying drawings,wherein:

FIG. 1 illustrates an example defibrillation scene, according to anexample implementation.

FIG. 2 illustrates a block diagram of an example defibrillator,according to an example implementation.

FIG. 3 illustrates a block diagram of another example defibrillator,according to an example implementation.

FIG. 4 illustrates a block diagram of an example computing system,according to an example implementation.

FIG. 5 illustrates an example system, according to an exampleimplementation.

FIG. 6 illustrates an example bracelet, according to an exampleimplementation.

FIG. 7 illustrates another example bracelet, according to an exampleimplementation.

FIG. 8 illustrates an example badge, according to an exampleimplementation.

FIG. 9 illustrates another example badge, according to an exampleimplementation.

FIG. 10 illustrates an example defibrillation pad, according to anexample implementation.

FIG. 11 illustrates another example defibrillation pad, according to anexample implementation.

FIG. 12 illustrates example event data, according to an exampleimplementation.

FIG. 13 shows a flowchart of an example of a method performed by adefibrillator, according to an example implementation.

FIG. 14 shows a flowchart of an example of a method performed by acomputing system, according to an example implementation.

FIG. 15 illustrates another example system, according to an exampleimplementation.

FIG. 16 illustrates another example system, according to an exampleimplementation.

FIG. 17 illustrates an example encoded version of an identifier of amedical device, according to an example implementation.

FIG. 18 illustrates another example encoded version of an identifier ofa medical device, according to an example implementation.

FIG. 19 shows a flowchart of an example of a method performed by amobile device, according to an example implementation.

DETAILED DESCRIPTION

Disclosed examples will now be described more fully hereinafter withreference to the accompanying drawings, in which some, but not all ofthe disclosed examples are shown. Indeed, several different examples maybe described and should not be construed as limited to the examples setforth herein. Rather, these examples are described so that thisdisclosure will be thorough and complete and will fully convey the scopeof the disclosure to those skilled in the art.

Currently, when a defibrillator, such as a public access defibrillatorAED, is applied to a patient in cardiac arrest in the field, thedefibrillator gathers data that can provide unique, valuable insightinto the cause of the cardiac arrest. That information can help aphysician in a hospital, minutes to hours later, when the physician isselecting a course of care for the patient. For example, if thephysician in the hospital does not know that the patient had ventricularfibrillation (VF) and was defibrillated in the field, the patient can bedischarged from the hospital without adequate measures to prevent ortreat another episode of VF.

For several reasons, it is a common problem that such AED data mightnever make it to the physician, and that the patient therefore fails toreceive appropriate care. Firstly, it is uncommon that the data from apublic access defibrillator AED is downloaded at all, and even moreuncommon that the data is provided promptly to medical professionalsthat need the data. Moreover, in one increasingly common scenario, soonafter the cardiac arrest, a public access defibrillator AED is appliedto the patient and delivers a shock. Thereafter, the patient resumesconsciousness. When professional healthcare responders subsequentlyarrive, the responders discover an alert patient and sometimes fail todetermine that a shock was delivered. Without that knowledge, theresponders might not recognize that the patient is vulnerable tofibrillation and, when the responders transfer the patient to hospitalstaff, the responders might fail to provide that key information. Aspublic access defibrillator AED use increases, these problems arebecoming increasingly common.

Example methods and systems describe several ways that event dataregarding treatment provided to a patient (e.g., while a defibrillatoris attached to the patient) can be identified and accessed by a medicalprofessional or other user. One example system includes a databaseresiding on a server in a network. The database stores data fromindividual cases, with data for respective cases having an associatedkey. The key for a given case is assigned to the case during the initialtreatment. That key then travels with the patient, and can subsequentlybe used to access the data for the patient's case from the database.Various techniques for assigning a key to a patient's case are describedherein.

Additional example methods and systems describe techniques for causing asummary of event data regarding treatment provided to a patient to betransmitted to a selected recipient for the event data. For example, amobile device can use an encoded version of an identifier of a medicaldevice that is provided on the medical device to cause a summary ofevent data gathered by the medical device to be transmitted to aselected recipient. The mobile device can use a camera of the mobiledevice to obtain an image of a quick-response (QR) code provided on themedical device.

In some examples, the medical device is configured to obtain event dataregarding treatment provided to a patient, and transmit the event datato a server. The mobile device can cause a summary of the event data tobe transmitted to the selected recipient by transmitting a request tothe server, with the request including an indication of the recipientand the identifier of the medical device. Reception of the request bythe server can then cause the server to generate the summary of theevent data and transmit the summary of the event data to the recipient.Alternatively, the mobile device can use the identifier of the medicaldevice to obtain the event data from the server. After obtaining theevent data, the mobile device can then generate the summary of the eventdata, and transmit the summary of the event data to the recipient.

Further details and features of these methods and systems are describedhereinafter with reference to the figures.

Referring now to the figures, FIG. 1 illustrates an exampledefibrillation scene 100. As shown in FIG. 1, a patient 102 is lying ontheir back. Patient 102 could be a patient in a public space, a home, apre-hospital environment, or even a hospital. A defibrillator 104 iscurrently being used to treat patient 102. As shown in FIG. 1,defibrillation pads 106, 108 of defibrillator 104 are applied to a chestof patient 102. Defibrillation pad 106 is coupled to defibrillator 104via an electrode lead 110. Defibrillation pad 108 is coupled todefibrillator 104 via an electrode lead 112. Defibrillation pads 106,108 and electrode leads 110, 112 are collectively referred to as atherapy cable 114. Defibrillator 104 can be used to deliver, via therapycable 114, a shock 116. Shock 116 can go through a heart 118 of patient102, in an attempt to restart heart 118, for saving the life of patient102.

Defibrillator 104 can be one of multiple different types, each withdifferent sets of features and capabilities. As one example,defibrillator 104 can be an AED, such as a public access defibrillatorAED. An AED can make a decision as to whether or not to deliver a shockto a patient automatically. For example, an AED can sense physiologicalconditions, such as shockable heart rhythms, of a patient viadefibrillation pads applied to the patient, and make the decision basedon an analysis of the patient's heart. Further, an AED can eitherdeliver the shock automatically, or instruct a user to deliver a shock,e.g., by pushing a button. AEDs can be operated by medical professionalsas well as people who are not in the medical profession, such aspolicemen, firemen, or even a person with first-aid and CPR/AEDtraining. AEDs can be located in public spaces or homes so thatlifesaving treatment can hopefully be initiated before medicalprofessionals arrive.

As another example, defibrillator 104 can be a more advanced device,such as a monitor defibrillator. Monitor defibrillators are intended tobe used by trained medical professionals, such as doctors, nurses,paramedics, emergency medical technicians, etc. As the name suggests, amonitor defibrillator is a combination of a monitor and a defibrillator.As a defibrillator, a monitor defibrillator can be one of differentvarieties, or even versatile enough to be able to switch among differentmodes that individually correspond to the varieties. One variety is thatof an automated defibrillator, which can determine whether a shock isneeded and, if so, charge to a predetermined energy level and instructthe user to deliver the shock. Another variety is that of a manualdefibrillator, where the user determines the need and controls deliveryof the shock. As a patient monitor, the monitor defibrillator hasfeatures additional to what is needed for operation as a defibrillator.These features can be for monitoring physiological indicators of apatient in an emergency scenario, for instance.

FIG. 2 illustrates an example AED 200. In FIG. 2, AED 200 includes aprocessor 202, a memory 204, a user interface 206, a communicationinterface 208, a power source 210, and a discharge circuit 212, eachconnected to a communication bus 214. AED 200 also includes anelectrical source 216 connected to discharge circuit 212, and a therapycable 218 connected to electrical source 216.

Memory 204 may include one or more computer-readable storage media thatcan be read or accessed by processor 202. The computer-readable storagemedia can include volatile and/or non-volatile storage components, suchas optical, magnetic, organic or other memory or disc storage, which canbe integrated in whole or in part with processor 202. The non-transitorydata storage is considered non-transitory computer readable media. Insome examples, the non-transitory data storage can be implemented usinga single physical device (e.g., one optical, magnetic, organic or othermemory or disc storage unit), while in other examples, thenon-transitory data storage can be implemented using two or morephysical devices.

The non-transitory data storage thus is a computer readable medium, andinstructions are stored thereon. The instructions include computerexecutable code.

Processor 202 may be a general-purpose processor or a special purposeprocessor (e.g., digital signal processor, application specificintegrated circuit, etc.). Processor 202 may receive inputs from othercomponents of AED 200 and process the inputs to generate outputs thatare stored in the non-transitory data storage. Processor 202 can beconfigured to execute instructions (e.g., computer-readable programinstructions) that are stored in the non-transitory data storage and areexecutable to provide the functionality of the AED described herein.

User interface 206 can take any of a number of forms. For example, userinterface 206 may include output devices, which can be visual, audibleor tactile, for communicating to a user. An output device can beconfigured to output a warning, which warns or instructs the patient ora bystander to do something. An output device can be a light or a screento display what is detected and measured, and provide visual feedback tothe rescuer for their resuscitation attempts. User interface 206 mayalso include a speaker, to issue voice prompts or sounds. User interface206 may also include a printer configured to print data on a piece ofpaper. User interface 206 may additionally include input devices forreceiving inputs from users. Such input devices may include variouscontrols, such as pushbuttons, keyboards, touchscreens, a microphone, afingerprint scanner, a retinal scanner, and/or a camera.

Communication interface 208 may be one or more wireless interfacesand/or one or more wireline interfaces that allow for both short-rangecommunication and long-range communication to one or more networks or toone or more remote devices. Such wireless interfaces may provide forcommunication under one or more wireless communication protocols, suchas Bluetooth, Wi-Fi (e.g., an institute of electrical and electronicengineers (IEEE) 802.11 protocol), Long-Term Evolution (LTE), cellularcommunications, near-field communication (NFC), radio-frequencyidentification (RFID), and/or other wireless communication protocols.Such wireline interfaces may include an Ethernet interface, a UniversalSerial Bus (USB) interface, or similar interface to communicate via awire, a twisted pair of wires, a coaxial cable, an optical link, afiber-optic link, or other physical connection to a wireline network.Communication interface 208 thus may include hardware to enablecommunication between AED 200 and other devices (not shown). Thehardware may include transmitters, receivers, and antennas, for example.

Power source 210 may include battery power, or a wired power means suchas an AC power connection.

Electrical source 216 can be configured to store electrical energy inthe form of an electrical charge, when preparing for delivery of ashock. Discharge circuit 212 can be controlled to permit the energystored in electrical source 216 to be discharged to defibrillation padsof therapy cable 218. Discharge circuit 212 can include one or moreswitches, such as an H-bridge. Processor 202 can instruct dischargecircuit 212 to output a shock using one of various energy levels. Theenergy levels can range from 50 Joules to 360 Joules. For instance, foran adult, processor 202 can select an energy level from an adult energysequence that includes energy levels of 200 Joules, 300 Joules, and 360Joules. Whereas, for a pediatric patient, processor 202 can select anenergy level from a pediatric energy sequence that includes energylevels of 50 Joules, 75 Joules, and 90 Joules.

Therapy cable 218 can be detachable from a housing of AED 200 by way ofa connector. The connector can be a tabbed, male connector that iscompatible with a port of AED 200. The defibrillation pads of therapycable 218 can be similar to defibrillation pads 106, 108 of FIG. 1. Thedefibrillation pads can include sensors that output physiologicmonitoring data measurements to processor 202. For example, thedefibrillation pads can include sensors that measure heart electricalactivity such as electrocardiogram (ECG).

After a shock is delivered, or in parallel with the instructing ofdischarge circuit 212 to deliver a shock, processor 202 can store dataindicative of the shock in memory 204. The data indicative of the shockcan include one or any combination of an energy level of the shock, atimestamp associated with the shock, an identification of AED 200, suchas a model number or serial number of AED 200, an indication of a numberof the shock (e.g., an indication that the shock is the first shock,second, shock, third shock, etc.), and an error code associated with theshock.

Additionally or alternatively, during a patient care event, processor202 can determine and store other data in memory 204. As one example,processor 202 can determine and store data indicating that return ofspontaneous circulation (ROSC) was achieved after delivering a shock.Processor 202 could determine that ROSC was achieved using one or moreof the following techniques: inferring that ROSC was achieved viaelectrical signals; detecting a motion artifact that does not correspondto compressions or moving a patient; determining whether a trend afterserval complete PQRST waveforms shows degradation; identifyingrespiratory breath from ECG; receiving information (e.g., wirelessly)from an accessory configured to deliver information to AED 200, such asblood pressure, SpO2, CO2, etc.; voice recognition that identifieskeywords such as “I feel a pulse!”. Processor 202 can also determinethat ROSC was achieved after delivering a shock based on receiving anindication from another device. For instance, processor 202 can senddata obtained by AED 200 to a server in network. The server, in turn,can analyze the data to determine whether or not the data is indicativeof ROSC being achieved (e.g., using any of the techniques noted above),and send to AED 200 data indicative of whether or not ROSC was achieved.

As another example, processor 202 can analyze ECG data, determine afibrillation type using the ECG data, and store an indication of thefibrillation type. Ventricular fibrillation (VF) can be qualified aseither refractory VF or recurrent VF. Refractory VF refers to VF thatpersists despite shock delivery. This is in contrast to recurrent VF,which is VF that re-appears after it had previously been terminated. Theindication of fibrillation type could therefore include an indication ofrefractory VF or an indication of recurrent VF. Similarly, processor 202can analyze ECG data, determine a coarseness of a VF waveform, and storean indication of the coarseness of the VF waveform. As still anotherexample, processor 202 can store an initial rhythm measured by AED 200,such as a few seconds of raw ECG data that is obtained before deliveryof any shocks. Processor 202 can also determine and store dataindicative of an algorithm used to measure the initial rhythm, such asdata indicative of a name of the algorithm. In some examples, processors202 can analyze ECG data and determine an amplitude spectrum area (AMSA)using the ECG data.

As yet another example, processor 202 can determine whether CPR is beingperformed, and then store in memory 204 data indicative of whether ornot CPR was performed on the patient. For example, processor 202 candetermine whether CPR is being performed based on analysis of impedancesignals received from the defibrillation pads of therapy cable 218. Asanother example, processor 202 can determine whether CPR is beingperformed based on an analysis of an ECG signal. CPR results in a veryrhythmic change in ECG signal. Processor 202 can detect such a changeusing signal processing. Such processing can involve providing the ECGsignal to a trained neural network that is configured to output anindication of whether the ECG signal is indicative of CPR beingperformed. The neural network can be trained using ECG signals that areknown to have been captured while CPR is being performed. The dataindicative of whether or not CPR was performed can include data forindividual compressions (e.g., compression rate data). Additionally oralternatively, the data indicative of whether or not CPR was performedcan include a binary indication (e.g., yes or no), or a qualitativeindication (e.g., no CPR; bad CPR; moderate CPR; good CPR; great CPR).Processor 202 can also determine and store in memory 204 and/or memory220 data indicative of whether or not AED 200 advised a user to continueCPR after a shock was delivered.

As yet another example, processor 202 can determine and then store inmemory 204 data indicative of whether any noise was detected during thepatient care event. Examples of noise include motion of the patient(e.g., chest compressions performed during analysis of the patient'sheart), the presence of an additional defibrillator attached to thepatient, detection of a pacemaker or other implantable device. In oneexample, processor 202 can detect such noise through signal processingof an ECG signal. Such signal processing can include performing aFourier transform, and analyzing the resulting frequency information.For instance, implanted electrical signal stimulator usually pulse veryrhythmically and, as a result, may be detectable from a Fouriertransform of an ECG signal.

Further, during or after the treatment is provided, AED 200 can uploadto a database event data regarding treatment provided to a patient. Forinstance, AED 200 can use communication interface 208 to transmit any ofthe data stored in memory 204 to a server, and the server can store theevent data in a database. Optionally, the server can analyze the eventdata and determine additional information. For instance, the server canperform any of the analysis processes mentioned above, such as analyzingECG data to identify one or more rhythms (e.g., VF), determine an AMSA,or detect a segment during which CPR is not being performed.

FIG. 3 illustrates an example monitor defibrillator 300. Like AED 200 ofFIG. 2, monitor defibrillator 300 includes a processor 302, a memory304, a user interface 306, a communication interface 308, a power source310, and a discharge circuit 312, each connected to a communication bus314. Monitor defibrillator 300 also includes an electrical source 316connected to discharge circuit 312, and a therapy cable 318 connected toelectrical source 316.

Unlike AED 200, monitor defibrillator 300 includes physiologicmonitoring sensors 320 and a sensor interface 322 that couplesphysiologic monitoring sensors 320 with processor 302. Physiologicmonitoring sensors 320 allow for monitoring physiological indicators ofa patient. Any number or type of sensors may be used depending ontreatment or monitoring of the patient. In many instances, a variety ofsensors are used to determine a variety of physiologic monitoring data.Physiologic monitoring data can include vital sign data (e.g., heartrate, respiration rate, blood pressure, and body temperature), as wellas signals from other sensors described herein. In addition, physiologicmonitoring data can also include treatment monitoring data, such aslocation at which an endotracheal tube has been placed or other sensorcontext information. The physiologic monitoring data can includetimestamps associated with a time of collection and may be considered ameasurement at a specific time. In some instances herein, physiologicmonitoring data refers to one measurement and data associated with theone measurement, and in other instances, physiologic monitoring datarefers to a collection of measurements as context indicates.

Physiologic monitoring sensors 320 can include sensors that measureheart electrical activity such as electrocardiogram (ECG), saturation ofthe hemoglobin in arterial blood with oxygen (SpO2), carbon monoxide(carboxyhemoglobin, COHb) and/or methemoglobin (SpMet), partial pressureof carbon dioxide (CO2) in gases in the airway by means of capnography,total air pressure in the airway, flow rate or volume of air moving inand out of the airway, blood flow, blood pressure such as non-invasiveblood pressure (NIBP) or invasive blood pressure (IP) by means of acatheter, core body temperature with a temperature probe in theesophagus, oxygenation of hemoglobin within a volume of tissue (rSO2),indicating level of tissue perfusion with blood and supply of oxygenprovided by that perfusion, and so forth.

Outputs, e.g., signals, from physiologic monitoring sensors 320 areconveyed to processor 302 by way of sensor interface 322. Processor 302records the signals and uses the signals for vital sign qualificationand caregiver feedback. In some examples, outputs from physiologicmonitoring sensors 320 or data derived from an analysis of the outputscan be recorded in a patient care record of monitor defibrillator 300and delivered to subsequent entities (e.g., hospital emergencydepartment, etc.) via communication interface 308.

Like AED 200 of FIG. 2, during or after treatment is provided by monitordefibrillator 300, monitor defibrillator 300 can upload to a databaseevent data regarding treatment provided to a patient. For instance,monitor defibrillator 300 can use communication interface 308 totransmit any of the data stored in memory 304 to a server, and theserver can store the event data in a database.

FIG. 4 illustrates an example computing system 400. Computing system 400can perform various acts and/or functions, such as those described inthis disclosure. Computing system 400 can include various components,such as processor 402, memory 404, communication interface 406, and/oruser interface 408. These components can be connected to each other (orto another device, system, or other entity) via connection mechanism410.

Processor 402 can include a general-purpose processor (e.g., amicroprocessor) and/or a special-purpose processor (e.g., a digitalsignal processor (DSP)).

Memory 404 can include one or more volatile, non-volatile, removable,and/or non-removable storage components, such as magnetic, optical, orflash storage, and/or can be integrated in whole or in part withprocessor 402. Further, memory 404 can take the form of a non-transitorycomputer-readable storage medium, having stored thereon programinstructions (e.g., compiled or non-compiled program logic and/ormachine code) that, when executed by processor 402, cause computingsystem 400 to perform one or more acts and/or functions, such as thosedescribed in this disclosure. As such, computing system 400 can beconfigured to perform one or more acts and/or functions, such as thosedescribed in this disclosure. Such program instructions can defineand/or be part of a discrete software application. In some instances,computing system 400 can execute program instructions in response toreceiving an input, such as from communication interface 406 and/or userinterface 408. Memory 404 can also store other types of data, such asthose types described in this disclosure.

Communication interface 406 can allow computing system 400 to connect toand/or communicate with another other entity according to one or moreprotocols. In one example, communication interface 406 can be a wiredinterface, such as an Ethernet interface or a high-definitionserial-digital-interface (HD-SDI). In another example, communicationinterface 406 can be a wireless interface, such as a cellular, WI-FI,RFID, and/or NFC interface. In this disclosure, a connection can be adirect connection or an indirect connection, the latter being aconnection that passes through and/or traverses one or more entities,such as such as a router, switcher, or other network device. Likewise,in this disclosure, a transmission can be a direct transmission or anindirect transmission.

User interface 408 can facilitate interaction between computing system400 and a user of computing system 400, if applicable. As such, userinterface 408 can include input components such as a keyboard, a keypad,a mouse, a touch-sensitive panel, a microphone, a camera, a fingerprintscanner, and/or a retinal scanner, and/or output components such as adisplay device (which, for example, can be combined with atouch-sensitive panel), a sound speaker, and/or a haptic feedbacksystem. More generally, user interface 408 can include hardware and/orsoftware components that facilitate interaction between computing system400 and the user of the computing system 400.

Computing system 400 can take various forms, such as a workstationterminal, a desktop computer, or a mobile device. Examples of mobiledevices include a mobile phone, a laptop, a tablet, or a wearablecomputing device.

FIG. 5 illustrates an example system 500. In line with the discussionabove, system 500 allows medical professionals or other users toidentify and access event data regarding treatment provided to apatient. As shown in FIG. 5, system 500 includes defibrillator 104,computing system 400, and a server 502. Server 502, in turn, includes adatabase 504 storing event data from individual cases. Event data for anindividual case is received from a defibrillator, such as defibrillator104. In addition, event data is accessible using a respective key. Thekey for an individual case is assigned to the individual case during apatient care event. The key is then associated with event data for theindividual case. In addition, that key then travels with the patientafter the patient leaves the patient care scene, and can subsequently beused to unlock and retrieve the event data for the patient's case. Forinstance, computing system 400 can obtain the key that travels with thepatient, and use the key to retrieve the event data from database 504.

A key can be associated with a patient's case in several ways. As oneexample, defibrillator 104 can associate a key with a patient's caseusing a near-field communication (NFC) chip. For instance, defibrillator104 can be equipped for future use by connecting it to a disposablecartridge that includes a set of defibrillation pads. Packaged in thecartridge with those defibrillator pads, and in close proximity to achassis of defibrillator 104 by virtue of the physical design, is apassive NFC chip. The NFC chip can be embedded within a bracelet orbadge that is attachable to the patient. Further, defibrillator 104includes an active NFC chip connected to a processor of defibrillator104.

During a patient care event, when defibrillator 104 is powered on,defibrillator 104 can use the active NFC chip to wirelessly transmit akey to the passive NFC chip included within the disposable cartridge.The key can include a number generated by defibrillator 104, such as arandomly generated number. In some examples, defibrillator 104 refrainsfrom writing the key to the passive NFC chip until defibrillator 104senses that defibrillation pads have been attached to the patient.Defibrillator 104 can determine whether or not the defibrillation padsare attached by sensing impedance using sensors of the defibrillationpads. Alternatively, during the patient care event, defibrillator 104can use the active NFC chip to read a key from the passive NFC chip.

Further, during the patient care event, following voice prompts issuedby defibrillator 104, an operator can open the disposable cartridge andapply the defibrillation pads to the patient. In addition, the operatorcan apply cardiopulmonary resuscitation (CPR) to the patient and/ordeliver one or more shocks. In line with the discussion above,defibrillator 104 can gather event data while defibrillator 104 isattached to the patient. Optionally, defibrillator 104 can write aportion or summary of the event data to the passive NFC chip.

At some point during use of defibrillator 104, such as when thedefibrillation pads are detached from the patient or when thedefibrillation pads are disconnected from defibrillator 104, voiceprompts from defibrillator 104 instruct the operator to remove abracelet having the embedded NFC chip from the disposable cartridge andplace it on the patient's wrist or ankle. Alternatively, the voiceprompts from defibrillator 104 can instruct the operator to remove abadge having the embedded NFC chip from the disposable cartridge andadhere the badge to a visible location on the patient (e.g., stick thebadge to a patient's chest or forearm). In some instances, defibrillator104 can continue to issue such voice prompts until the active NFC chipof defibrillator 104 no longer detects the presence of the passive NFCchip, indicating that the passive NFC chip has been removed from thedisposable cartridge.

Either during the patient care event, at the end of the patient careevent, or at later time when defibrillator 104 establishes a connectionto server 502, defibrillator 104 transmits event data and the key toserver 502. Server 502 then uses the key to validate requests for accessto the event data. For example, in order to access event data, computingsystem 400 provides the key to server 502. Server 502 then determineswhether database 504 includes any event data associated with thereceived key. If so, server 502 transmits the event data associated withthe received key to computing system 400.

In some examples, server 502 also uses a second level of validation whenresponding to requests for event data. For instance, a user of computingsystem 400 can provide credentials proving that the user is a licensedhealthcare provider. Computing system 400 can send the credentials toserver 502 (or another server) to verify the credentials. The verifyingof credentials can occur in an automated manner (e.g., by cross-checkinginformation with a database), or through interaction with a customerservice representative. After the credentials are verified, computingsystem 400 can then request event data form server 502. Based on thecredentials of the user of the computing system 400 having beenverified, server 502 can then respond to the request for event data.

In some examples, server 502 can apply analytics to the event data toderive useful summary information from the event data. The summaryinformation can include a detected rhythm(s) or AMSA determined usingECG data, for instance. The summary information can also include asegment of ECG data that is annotated as being ECG data that correspondsto a time when CPR was not being performed.

Later in the course of care of the patient, such as a few hours or dayslater, a medical professional can use computing system 400 to read thekey from the NFC chip embedded within the bracelet or badge. Thebracelet or badge might still be attached to the patient at this time.For instance, computing system 400 can be a mobile device having an NFCdevice that is configured to read NFC chips. Optionally, computingsystem 400 can read a portion or summary of the event data from the NFCchip embedded within the bracelet or badge.

Alternatively, instead of using NFC technology to associate a key with apatient, defibrillator 104 can use radio-frequency identification (RFID)technology to associate a key with a patient. With this approach, thebracelet or badge packaged within the disposable cartridge can includean embedded RFID tag that stores a key. At the patient care scene,defibrillator 104 can read the key using an RFID reader. Similarly,during subsequent patient care, computing system 400 can read the keyusing an RFID reader.

Defibrillator 104 can also use a quick response (QR) code to associate akey with a patient's case. For instance, a bracelet or badge packagedwithin the disposable cartridge can include a QR code printed on thebracelet or badge. The QR code can encode a key. Defibrillator 104 candetermine the key by reading the QR code with a QR code reader whendefibrillator is being prepared for future use. Alternatively,defibrillator 104 can determine the key by accessing configurationinformation that is programmed for defibrillator 104 prior to use ofdefibrillator 104. For instance, a user can use a user interface ofdefibrillator 104 or a defibrillator configuration program accessible toa system administrator to provide the key. The key could be printed onpackaging for the disposable cartridge, such that the user could readthe key and then program the configuration information. Or a user caninsert a memory card into defibrillator 104, with the memory cardstoring the key, and defibrillator 104 can read the memory card todetermine the key. During subsequent patient care, computing system 400can determine the key by reading the QR code using a QR code reader.

In some examples, a badge or bracelet might not be able to wirelesslycommunicate with defibrillator 104. For instance, a badge or braceletmight have a memory card. While the badge or bracelet is packaged withinthe disposable cartridge, the memory card can be communicatively coupledto defibrillator 104 using a wired connection. During the patient careevent, defibrillator 104 can write a key to the memory card. Optionally,defibrillator 104 can also write the event data gathered bydefibrillator 104, or a summary or portion of the event data, to thememory card. After use of defibrillator 104 ends, defibrillator 104 mayprompt a user (e.g., by way of voice prompts) to remove the bracelet orbadge and apply the bracelet or badge to the patient.

During subsequent patient care, computing system 400 can read the keyfrom the memory card, and use the key to access the event data fromserver 502. Additionally or alternatively, if the memory card alsoincludes event data, the computing system 400 can also read the eventdata from the memory card. In some instances, the memory card can be aremovable memory card. In other instances, the bracelet or badge caninclude a communication port that facilitates transferring data from thememory card to computing system using a data cable.

Further, in some examples, the bracelet can be designed such that accessto the memory card of the bracelet or badge is not possible withoutcutting the bracelet off the patient. For instance, the memory cardmight only be removable from an inner side of the bracelet, such thatwhile the bracelet is being worn, the memory card cannot be removed.

In some examples, the bracelet or badge can display a timer that isindicative of a time that treatment is provided to the patient, such asa time that the bracelet or badge is removed from the disposablecartridge or a time that the defibrillator is powered on. With oneapproach, the bracelet or badge can include an insulating strip that ispositioned between one side of a battery and a portion of a timercircuit. Removal of the insulating strip can cause the timer to begin.The insulating strip might be attached to the disposable cartridge, suchthat removal of the bracelet or badge from the disposable cartridgecauses the insulating strip to be removed from the bracelet or badge andthe timer to start. With another approach, the timer can be configuredto begin in response to receiving a communication signal fromdefibrillator 104. For instance, defibrillator 104 can send thecommunication signal to the bracelet or badge when defibrillator 104 ispowered on.

FIGS. 6 and 7 illustrate example bracelets 600, 700 that can be includedwithin a disposable cartridge for a defibrillator. As shown in FIG. 6,bracelet 600 includes a QR code 602, a communication device 604, and atimer 606. In line with the discussion above, communication device 604can include a NFC chip or an RFID tag.

As shown in FIG. 7, bracelet 700 similarly includes a QR code 702 and atimer 706. However, unlike bracelet 600 of FIG. 6, bracelet 700 includesa memory card 708 and a communication port 710. A computing system, suchas computing system 400 of FIG. 5, can read data from memory card 708 byconnecting a data cable to communication port 710. Alternatively, a usercan remove memory card 708 from bracelet 700 and insert memory card 708into a memory card reader of a computing system to read data from memorycard 708.

Bracelet 600 or bracelet 700 can be packaged within a cartridge for adefibrillator. For instance, a cartridge can include a firstdefibrillation pad, a second defibrillation pad, and bracelet 600 orbracelet 700.

FIGS. 8 and 9 illustrate example badges 800, 900 that can be includedwithin a disposable cartridge for a defibrillator. As shown in FIG. 8,badge 800 includes a QR code 802, a communication device 804, and atimer 806. In line with the discussion above, communication device 804can include a NFC chip or an RFID tag. Badge 800 can include an adhesivelayer that is covered by a removable backing (not shown). A user canapply badge 800 to a patient by removing the removable backing, andadhering badge 800 to the patient using the adhesive layer.

As shown in FIG. 9, badge 900 similarly includes a QR code 902 and atimer 906. However, unlike badge 800 of FIG. 8, badge 900 includes amemory card 908 and a communication port 910. A computing system, suchas computing system 400 of FIG. 5, can read data from memory card 908 byconnecting a data cable to communication port 910. Alternatively, a usercan remove memory card 908 from badge 900 and insert memory card 908into a memory card reader of a computing system to read data from memorycard 908.

Badge 800 or badge 900 can be packaged within a cartridge for adefibrillator. For instance, a cartridge can include a firstdefibrillation pad, a second defibrillation pad, and badge 800 or badge900.

A key can also be associated with a patient's case by usingdefibrillation pads that are designed with the capability of placing atemporary tattoo on the patient's skin. By way of example, one or bothdefibrillation pads can be manufactured with ink that is placed on thesurface of the defibrillation pad's adhesive gel such that, whenapplied, the defibrillation pads will leave a QR code imprinted on thepatient's skin. Defibrillator 104 can determine the key by reading theQR code with a QR code reader when defibrillator is being prepared forfuture use. Alternatively, defibrillator 104 can determine the key byaccessing configuration information that is programmed for defibrillator104 prior to use of defibrillator 104. For instance, a user can use auser interface of defibrillator 104 or a defibrillator configurationprogram accessible to a system administrator to provide the key. The keycould be printed on packaging for the disposable cartridge, such thatthe user could read the key and then program the configurationinformation. Or a user can insert a memory card into defibrillator 104,with the memory card storing the key, and defibrillator 104 can read thememory card to determine the key. During subsequent patient care,computing system 400 can determine the key by reading the QR code usinga QR code reader.

FIG. 10 illustrates an example defibrillation pad 1000. As shown in FIG.10, defibrillation pad 1000 is designed to imprint an encoded version ofa key 1002 on a skin of a patient 1004 when applied. Defibrillation pad1000 includes a flexible substrate 1006. Defibrillation pad 1000 canfurther include a removable backing attached to a first side 1008 offlexible substrate 1006 as well as an adhesive gel provided betweenfirst side 1008 of flexible substrate 1006 and the removable backing. Inaddition, a layer of ink can be provided on the adhesive gel such that,when flexible substrate 1006 is applied to patient 1004, the layer ofink imprints encoded version of the key 1002 on the skin of patient1004. In FIG. 10, encoded version of the key 1002 is a QR code.

In some examples, a defibrillation pad can be designed with thecapability of placing a temporary tattoo on the patient's skin only ifand when a defibrillation shock is delivered to the patient. By way ofexample, one or both defibrillation pads can be manufactured withcollection of vesicles that contain ink and only rupture and release theink if exposed to electric current of the large amplitude encounteredduring a defibrillation shock.

FIG. 11 illustrates an example defibrillation pad 1100. Likedefibrillation pad 1000 of FIG. 10, defibrillation pad 1100 is designedto imprint an encoded version of a key 1102 on a skin of a patient 1104when applied. However, unlike defibrillation pad 1000, defibrillationpad 1100 is designed to imprint the encoded version of the key only ifand when a defibrillation shock is applied to the patient. To accomplishthis, defibrillation pad 1100 includes a flexible substrate 1106.Defibrillation pad 1100 can further include a removable backing attachedto a first side 1108 of flexible substrate 1106 as well as an adhesivegel provided between first side 1108 of flexible substrate 1106 and theremovable backing. In addition, a collection of vesicles 1110 is beprovided on the adhesive gel. Collection of vesicles 1110 include inkand are configured to rupture when an electric current of sufficientamplitude (e.g., an amplitude that is greater than or equal to theamplitude encountered during a defibrillation shock) is applied todefibrillation pad 1100. Upon rupturing, the ink within collection ofvesicles 1110 imprints encoded version of the key 1102 on the skin ofpatient 1104. In FIG. 11, encoded version of the key 1102 is a QR code.

In other examples, a defibrillator can obtain a key using a fingerprintscanner or a retinal scanner. At some point during the patient careevent, a user can scan a fingerprint of the patient or obtain a retinaimage from the patient. The fingerprint or retina image can then serveas the key. For instance, during subsequent patient care, computingsystem 400 can obtain the fingerprint or retina image, and use thefingerprint or retina image to access the event data from server 502.

Similarly, in some examples, a defibrillator can obtain a key byobtaining an image of an identification card (e.g., a driver's licenseor a passport). During subsequent patient care, computing system 400 canobtain an image of the same identification card, and use the image toaccess the event data from server 502.

FIG. 12 illustrates example event data 1200 that can be displayed on acomputing system, such as computing system 400 of FIG. 5. As shown inFIG. 12, event data 1200 includes physiologic monitoring data obtainedusing a sensor of a defibrillator. Event data 1200 includes a fewseconds of ECG data surrounding delivery of a shock. In the example ofFIG. 12, event data 1200 corresponds to a second shock from among threeshocks that were delivered to a patient during a patient care event. Amedical professional can view ECG data surrounding the other two shocksusing user interface elements 1202, 1204. Event data 1200 is alsolabeled with an indication of a detected rhythm, namely, ventricularfibrillation. Further, event data 1200 indicates an energy level of theshock. Still further, event data 1200 includes a timestamp indicative ofwhen the defibrillator was used. The displayed ECG data can include ECGdata obtained while CPR was not being performed on the patient (e.g.,during a pause in CPR).

FIG. 13 shows a flowchart of an example of a method 1300 performed by adefibrillator. Method 1300 shown in FIG. 13 presents an example of amethod that could be performed by a defibrillator, such as the AED 200shown in FIG. 2 or the monitor defibrillator 300 shown in FIG. 3, forexample. Further, devices or systems may be used or configured toperform logical functions presented in FIG. 13. In some instances,components of the devices and/or systems may be configured to performthe functions such that the components are actually configured andstructured (with hardware and/or software) to enable such performance.In other examples, components of the devices and/or systems may bearranged to be adapted to, capable of, or suited for performing thefunctions, such as when operated in a specific manner. Method 1300 mayinclude one or more operations, functions, or actions as illustrated byone or more of blocks 1302-1308. Although the blocks are illustrated ina sequential order, these blocks may also be performed in parallel,and/or in a different order than those described herein. Also, thevarious blocks may be combined into fewer blocks, divided intoadditional blocks, and/or removed based upon the desired implementation.

It should be understood that for this and other processes and methodsdisclosed herein, flowcharts show functionality and operation of onepossible implementation of present examples. In this regard, each blockor portions of each block may represent a module, a segment, or aportion of program code, which includes one or more instructionsexecutable by a processor for implementing specific logical functions orsteps in the process. The program code may be stored on any type ofcomputer readable medium or data storage, for example, such as a storagedevice including a disk or hard drive. Further, the program code can beencoded on a computer-readable storage media in a machine-readableformat, or on other non-transitory media or articles of manufacture. Thecomputer readable medium may include non-transitory computer readablemedium or memory, for example, such as computer-readable media thatstores data for short periods of time like register memory, processorcache and Random Access Memory (RAM). The computer readable medium mayalso include non-transitory media, such as secondary or persistentlong-term storage, like read only memory (ROM), optical or magneticdisks, compact-disc read only memory (CD-ROM), for example. The computerreadable media may also be any other volatile or non-volatile storagesystems. The computer readable medium may be considered a tangiblecomputer readable storage medium, for example.

In addition, each block or portions of each block in FIG. 8, and withinother processes and methods disclosed herein, may represent circuitrythat is wired to perform the specific logical functions in the process.Alternative implementations are included within the scope of theexamples of the present disclosure in which functions may be executedout of order from that shown or discussed, including substantiallyconcurrent or in reverse order, depending on the functionality involved,as would be understood by those reasonably skilled in the art.

At block 1302, method 1300 includes obtaining, by a defibrillator, eventdata regarding treatment provided to a patient. The treatment isprovided to the patient while the defibrillator is attached to thepatient. The event data can include physiologic monitoring data obtainedusing a sensor of the defibrillator, such as ECG data. Further, the ECGdata can include ECG data obtained before any shocks are delivered tothe patient by the defibrillator and/or ECG data obtained while CPR isnot being performed on the patient. The event data can also includeaudio data or video data.

In addition, obtaining the event data can involve obtaining physiologicmonitoring data using a sensor of the defibrillator, and then analyzingthe physiologic monitoring data so as to obtain the event data. Forinstance, the defibrillator can determine an AMSA using ECG data.

At block 1304, method 1300 includes obtaining, by the defibrillator, akey that facilitates validating a request from a computing device toaccess the event data. In one example, obtaining the key can involvegenerating a number using a processor of the defibrillator. In otherexamples, obtaining the key can involve reading the key from an RFIDtag, reading a QR code using a QR code reader, or reading the key froman NFC chip using an NFC device. The RFID tag, QR code, or NFC chip canbe provided on a bracelet or a badge. In still other examples, obtainingthe key can involve obtaining an image of a fingerprint of the patientusing a fingerprint scanner, obtaining a retina image from the patientusing a retinal scanner, or obtaining an image of an identification cardof the patient using a camera.

At block 1306, method 1300 includes associating, by the defibrillator,the key with the event data. For instance, after obtaining the key, thedefibrillator can store the key and the event data together within anevent data file. Further, at block 1308, method 1300 includestransmitting, by the defibrillator, the key and the event data to aserver in a network for storage. For instance, the defibrillator cantransmit an event data file including the key and the event data to theserver.

In some examples, method 1300 also includes writing the key on an NFCchip or a removable memory card. For instance, after generating anumber, the defibrillator can write the key on an NFC chip or aremovable memory card. Further, the writing of the key can occur basedon determining that defibrillation pads are attached to the patient.

In examples in which the key is stored in a removable memory card, thedefibrillator can prompt an operator to attach the removable memory cardto the patient. For instance, the defibrillator can provide voiceprompts that instruct the operator to attach the removable memory cardto the patient.

Similarly, in examples in which the key is provided on or stored on abracelet or badge, method 1300 can also include prompting an operator toattach the bracelet or badge to the patient. For instance, thedefibrillator can provide voice prompts that instruct the operator toattach the bracelet or badge to the patient.

FIG. 14 shows a flowchart of an example of a method performed by acomputing system. Method 1400 shown in FIG. 14 presents an example of amethod that could be performed by computing system 400 of FIGS. 4 and 5,for example. Further, devices or systems may be used or configured toperform logical functions presented in FIG. 14.

At block 1402, method 1400 includes obtaining, using a computing system,a key associated with event data regarding treatment provided to apatient using a defibrillator. The treatment is provided to the patientwhile a defibrillator is attached to the patient.

In some examples, obtaining the key can involve reading the key from anNFC chip, an RFID tag, or a QR code. The NFC chip, RFID tag, or QR codecan be provided on a bracelet or a badge that is attached to thepatient. Alternatively, the QR code can be provided on a temporarytattoo. Further, in some examples, obtaining the key can involveobtaining a fingerprint, obtaining a retinal image, or obtaining animage of an identification card. Still further, obtaining the key caninvolve reading the key from a removable memory card.

At block 1404, method 1400 includes transmitting, by the computingsystem, the key to a server in a network. At block 1406, method 1400includes responsive to transmitting the key to the server, receiving, bythe computing system from the server, the event data associated with thekey. And at block 1408, method 1400 includes displaying, by thecomputing system, a portion of the event data.

The event data can include physiologic monitoring data obtained using asensor of the defibrillator, such as ECG data. Further, the ECG data caninclude ECG data obtained before any shocks are delivered to the patientby the defibrillator and/or ECG data obtained while CPR is not beingperformed on the patient. The event data can also include audio data orvideo data.

FIG. 15 illustrates an example system 1500. In line with the discussionabove, system 1500 allows a summary of event data regarding treatmentprovided to a patient to be transmitted to a selected recipient for theevent data. Like system 500 of FIG. 5, system 1500 includes computingsystem 400 as well as server 502. Server 502, in turn, includes database504 storing event data for individual cases. Event data for individualcases is received from medical devices, such as medical device 1506.

System 1500 also includes a mobile device 1508. Mobile device 1508 cancause a summary of the event data obtained by medical device 1506 to betransmitted to the selected recipient by transmitting to server 502 arequest, with the request including an indication of the recipient andidentifier of medical device 1506 or an encoded version of theidentifier. Reception of the request by server 502 can then cause server502 to generate the summary of the event data and transmit the summaryof the event data to the recipient. For instance, server 502 cantransmit the summary of the event data to computing system 400.Computing system 400 can include a computing system that recipient usesto access email communications, or a dedicated computing system that islocated at a medical provider and connected to a medical alert system.

Medical device 1506 can include any type of pre-hospital device (e.g.,advanced life support device or accessory), emergency response device(e.g., basic life support device or accessory), or public access devices(e.g., an AED or AED accessory). Examples of medical devices include adefibrillator, monitor defibrillator, PAD AED, chest compression system,CPR coaching device, or laryngoscope.

During a patient care event, at the end of a patient care event, or at alater time when medical device 1506 establishes a connection to server502, medical device 1506 transmits event data to server 502. Server 502then stores the event data in database 504. Server 502 stores the eventdata in a manner that allows for subsequently accessing the event datausing an identifier of medical device 1506.

In some examples, server 502 can apply analytics to the event data toderive useful summary information from the event data. For instance, thesummary information can include a detected rhythm(s) or AMSA determinedusing ECG data, for instance. The summary information can also include asegment of ECG data that is annotated as being ECG data that correspondsto a time when CPR was not being performed.

Mobile device 1508 can take the form of a smartphone, tablet, orwearable computing device, for instance. Mobile device 1508 can obtainan encoded version of an identifier of medical device 1506, obtain aselection of a recipient for the event data, and cause server 502 totransmit a summary of the event data to the recipient. By way ofexample, an application on mobile device 1508 can instruct a user toread a QR code using mobile device 1508. The QR code can be provided ona label that is attached to medical device 1506, displayed on a displayof medical device 1506, or printed on a piece of paper by medical device1506, for instance. After reading the QR code, the application on mobiledevice 1508 can prompt the user to select a recipient for the eventdata. After receiving a selection of the recipient, mobile device 1508can transmit a request to server 502. The request can include therecipient and either the encoded version of the identifier of medicaldevice 1506 or the identifier of medical device 1506.

In some examples, mobile device 1508 can display a list of recipients.Mobile device 1508 can populate the list based on medical providers(e.g., hospitals) that are located within a threshold distance of alocation of medical device 1508. Alternatively, mobile device 1508 canpopulate the list based on configuration information previouslyconfigured by the user or a system administer. The list can display oneor more physical addresses (e.g., street number and name and/or city) ornames (e.g., hospital department and name). Mobile device 1508 canassociate the physical addresses and names with email addresses ordevice names. Medical device 1508 can also prompt the user to select arecipient by inputting an address for the recipient (e.g., an emailaddress or a name of a device that is connected to a medical alertsystem).

In some examples, mobile device 1508 can send the request to server 502before the patient care event is completed. With this approach, server502 can send a summary of event data to the recipient after server 502receives the event data. Alternatively, the request can designate a timeor multiple times for summaries of event data to be sent (e.g., at theend of the patient care event or after expiration of a given period oftime (e.g., thirty minutes).

In some examples, the application on mobile device 1508 can allow theuser to provide additional information, such as text, images, or videos.Server 502 can then add the additional information to the summary of theevent data that is transmitted to the recipient. Further, theapplication on mobile device 1508 can require the user to login to anaccount before allowing the user to use the application.

In alternative method of operation, the application on mobile device1508 might not require a user to select a recipient for the event data.Instead, mobile device 1508 can be configured to automatically cause asummary of the event data to be transmitted to devices that areregistered with a medical alert system and within a threshold distanceof a location of mobile device 1508. The automatic transmission canoccur after the application on mobile device 1508 obtains the image ofthe encoded version of the identifier of medical device 1506.

Further, mobile device 1508 can be configured to obtain and store devicedata indicative of properties of medical device 1506. For instance,mobile device 1508 can obtain from server 502 device data that isindicative of a serial number, battery level, or expiration date formedical device 1506 or an accessory of medical device 1506. After apatient care event, a user can re-visit the device data to reviewproperties of medical device 1506. For privacy/security reasons, thedevice data does not include any patient-related information.

Mobile device 1508 can also determine a location of mobile device 1508,and send the location or information derived from the location to server502 for inclusion in the summary of event data. For instance, mobiledevice 1508 can determine a travel time from the location of mobiledevice 1508 to a location of the recipient, and send the travel time toserver 502. Server 502 can then include the travel time in the summaryof the event data. Alternatively, server 502 can determine the traveltime using the location of the mobile device and the location of therecipient.

The summary of event data can take the form of a portable documentformat (PDF) file. For instance, server 502 can generate the summary ofevent data by inserting portions of the event data into different fieldsof the PDF file. The summary of the event data can include one or moreof ECG data, impedance values, an initial detected rhythm, number ofshocks, SpO2, CO2, CPR depth, or CPR rate, for example. Server 502 canidentify the appropriate event data using the identifier of medicaldevice 1506 or the encoded version of the identifier of medical device1506. When the identifier is encoded, server 502 can decode theidentifier to determine the identifier. In some examples, server 502 canalso use a timestamp associated with a request to identify theappropriate event data. The timestamp can allow the server 502 todistinguish between two sets of event data that are associated with thesame medical device but correspond to different patient care events,such as patient care events occurring on different days.

FIG. 16 illustrates an example system 1600. System 1600 allows mobiledevice 1508 to transmit a summary of event data regarding treatmentprovided to a patient to a selected recipient for the event data. Likesystem 1500 of FIG. 15, system 1600 includes server 502, computingsystem 400, medical device 1506, and mobile device 1508. System 1600differs from system 1500 in that mobile device uses the identifier ofmedical device 1506 to obtain event data gathered by medical device1506, and then generates the summary of event data and transmits thesummary of the event data to the recipient. For instance, afterobtaining the encoded version of the identifier of medical device 1506,mobile device 1508 decodes the encoded version of the identifier so asto obtain the identifier. Mobile device 1508 then transmits a request toserver 502, with the request including identifier, and receives theevent data. Further, mobile device generates a summary of the eventdata, and transmits the summary of the event data to the recipient. Likein system 1500, generating the summary of the event data can involvepreparing a PDF file using portions of the event data.

FIG. 17 illustrates an example encoded version of an identifier 1700 ofa medical device 1702. As shown in FIG. 17, encoded version of theidentifier 1700 is a QR code. The QR code is provided on a label that isattached to a housing of medical device 1702.

FIG. 18 illustrates another example encoded version of an identifier1800 of medical device 1702. As shown in FIG. 18, encoded version of theidentifier 1800 is also a QR code. However, in FIG. 17, in FIG. 18, theQR code is displayed on a display of medical device 1802. This allowsfor generation of QR codes that change over time. With this approach,each individual case for which medical device 1702 obtains event datacan have a unique QR code.

FIG. 19 shows a flowchart of an example of a method performed by amobile device, according to an example implementation. Method 1900 shownin FIG. 19 presents an example of a method that could be performed bymobile device 1508 of FIGS. 15 and 16, for example. Further, devices orsystems may be used or configured to perform logical functions presentedin FIG. 19.

At block 1902, method 1900 includes obtaining, by a mobile device, anencoded version of an identifier of a medical device. The medical deviceis configured to obtain event data regarding treatment provided to apatient, and to transmit the event data to a server.

The encoded version of the identifier can be provided on a label that isattached to the medical device. Alternatively, the encoded version ofthe identifier can be displayed by a display of the medical device orprinted on a piece of paper by the medical device. In some examples,obtaining the encoded version of the identifier involves reading a QRcode using a QR code reader.

The event data can include physiologic monitoring data obtained using asensor of the defibrillator, such as ECG data. Further, the ECG data caninclude ECG data obtained before any shocks are delivered to the patientby the defibrillator and/or ECG data obtained while CPR is not beingperformed on the patient. The event data can also include audio data orvideo data.

At block 1904, method 1900 includes obtaining, by the mobile device, aselection of a recipient for the event data. The recipient can includean email address associated with a medical provider. Alternatively, therecipient can include a device that is located at a medical provider andconnected to a medical alert system. In some examples, obtaining theselection of the recipient can involve obtaining a selection of therecipient from among a list of recipients displayed by the mobiledevice.

At block 1906, method 1900 includes causing, by the mobile device, asummary of the event data to be transmitted to the recipient. Thesummary of the event data can include a PDF file. In one example,causing the summary of the event data to be transmitted to the recipientinvolves: decoding the encoded version of the identifier of the medicaldevice so as to obtain the identifier of the medical device, andtransmitting to a server a request that includes: an indication of therecipient and the identifier of the medical device. Receipt of therequest by the server then causes the server to generate the summary ofthe event data to the recipient.

In another example, causing the summary of the event data to betransmitted to the recipient involves transmitting to a server a requestthat includes: an indication of the recipient and the encoded version ofthe identifier of the medical device. Receipt of the request by theserver then causes the server to generate the summary of the event datato the recipient.

In yet another example, causing the summary of the event data to betransmitted to the recipient involves: decoding the encoded version ofthe identifier of the medical device so as to obtain the identifier ofthe medical device, obtaining the event data from a server using theidentifier of the medical device, generating the summary of the eventdata, and transmitting the summary of the event data to the recipient.

In some examples, the event data can include device data indicative ofproperties of the medical device. Method 1900 can then involve storingthe device data on the mobile device.

Method 1900 can also include determining a location of the mobiledevice. Further, the summary of the event data can include an indicationof a travel time from the location of the mobile device to a location ofthe recipient, or an indication of the location of the mobile device.

The systems and methods described herein are very beneficial forproviding better patient care after a cardiac event. Informationgathered by a defibrillator can provide unique, valuable insight intothe cause of a cardiac event. That information can be beneficial to aphysician in a hospital, minutes to hours later, when she is selectingthe appropriate course of care for that patient. For example, if thephysician does not know that the patient had VF and was defibrillated inthe field, the patient might be discharged from the hospital withoutadequate measures to prevent or treat another episode of VF.

Further, the systems and methods described herein provide efficient waysto provide data gathered by a medical device to a recipient, such as amedical professional that will provide subsequent care for the patient.Providing this data to the recipient allows the recipient to providebetter care and proper preparation for an incoming patient.

By the term “substantially” and “about” used herein, it is meant thatthe recited characteristic, parameter, or value need not be achievedexactly, but that deviations or variations, including for example,tolerances, measurement error, measurement accuracy limitations andother factors known to skill in the art, may occur in amounts that donot preclude the effect the characteristic was intended to provide.

Different examples of the system(s), device(s), and method(s) disclosedherein include a variety of components, features, and functionalities.It should be understood that the various examples of the system(s),device(s), and method(s) disclosed herein may include any of thecomponents, features, and functionalities of any of the other examplesof the system(s), device(s), and method(s) disclosed herein in anycombination or any sub-combination, and all of such possibilities areintended to be within the scope of the disclosure.

The description of the different advantageous arrangements has beenpresented for purposes of illustration and description, and is notintended to be exhaustive or limited to the examples in the formdisclosed. Many modifications and variations will be apparent to thoseof ordinary skill in the art. Further, different advantageous examplesmay describe different advantages as compared to other advantageousexamples. The example or examples selected are chosen and described inorder to best explain the principles of the examples, the practicalapplication, and to enable others of ordinary skill in the art tounderstand the disclosure for various examples with variousmodifications as are suited to the particular use contemplated.

What is claimed is:
 1. A defibrillation pad comprising: a flexiblesubstrate; a removable backing attached to a first side of the flexiblesubstrate; an adhesive gel provided between the first side of theflexible substrate and the removable backing; and a layer of inkprovided on the adhesive gel such that, when the removable backing isremoved and the flexible substrate is applied to a patient, the layer ofink imprints an encoded version of a key on a skin of the patient. 2.The defibrillation pad of claim 1, wherein the encoded version of thekey comprises a quick response (QR) code.
 3. The defibrillation pad ofclaim 1, wherein the key facilitates validating a request from acomputing system to access event data regarding treatment provided tothe patient using a defibrillator.
 4. A defibrillation pad comprising: aflexible substrate; a removable backing attached to a first side of theflexible substrate; an adhesive gel provided between the first side ofthe flexible substrate and the removable backing; and a collection ofvesicles provided on the adhesive gel, wherein vesicles of thecollection of vesicles comprise ink and are configured to rupture whenan electric current is applied to the defibrillation pad.
 5. Thedefibrillation pad of claim 4, wherein the collection of vesicles areconfigured to rupture when an electric current having an amplitude thatsatisfies a threshold condition is applied to the defibrillation pad. 6.The defibrillation pad of claim 4, wherein the collection of vesiclesare arranged such that an encoded version of a key is imprinted on apatient's skin when the removable backing is removed, the flexiblesubstrate is applied to a patient, and the electric current is appliedto the defibrillation pad.
 7. The defibrillation pad of claim 6, whereinthe encoded version of the key comprises a quick response (QR) code. 8.The defibrillation pad of claim 6, wherein the key facilitatesvalidating a request from a computing system to access event dataregarding treatment provided to the patient using a defibrillator.
 9. Acartridge for a defibrillator, the cartridge comprising: a firstdefibrillation pad; a second defibrillation pad; and a braceletcomprising a memory, the memory configured to store a key thatfacilitates validating a request from a computing system to access eventdata, wherein the event data relates to treatment provided to a patientwhile the defibrillator is attached to the patient.
 10. The cartridge ofclaim 9, wherein the bracelet further comprises a near-fieldcommunication (NFC) chip, and wherein the memory is a memory of the NFCchip.
 11. The cartridge of claim 9, wherein the bracelet furthercomprises a radio-frequency identification (RFID) tag, and wherein thememory is a memory of the RFID tag.
 12. The cartridge of claim 9,wherein the bracelet further comprises a display configured to display atimer that is indicative of a time that the treatment is provided to thepatient.
 13. The cartridge of claim 12, wherein the timer is indicativeof a time that the bracelet is removed from the cartridge.
 14. Thecartridge of claim 12, wherein the timer is indicative of a time thatthe defibrillator is powered on.
 15. The cartridge of claim 9, furthercomprising a communication port that facilitates transferring databetween the memory and the defibrillator or another computing system.16. The cartridge of claim 9, wherein the memory comprises a removablememory card.
 17. The cartridge of claim 16, wherein the removable memorycard is unable to be removed while the bracelet is being worn by thepatient.
 18. The cartridge of claim 9, further comprising a quickresponse (QR) code that encodes the key.
 19. The cartridge of claim 18,wherein the QR code is provided on packaging for the cartridge.
 20. Thecartridge of claim 18, wherein the QR code is provided on the bracelet.